Bug 1810470: carry: Check for optimizing state too#167
Bug 1810470: carry: Check for optimizing state too#167openshift-merge-robot merged 1 commit intoopenshift:masterfrom
Conversation
Without checking for optimizing state the resizing operation takes far too long and hence we are going to bring it back.
|
@gnufied: This pull request references Bugzilla bug 1810470, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
openshift-ci-robot
added
bugzilla/severity-medium
openshift-ci-robot
added
the
approved
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gnufied, huffmanca The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@gnufied: All pull requests linked via external trackers have merged:
Bugzilla bug 1810470 has been moved to the MODIFIED state. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
4 participants
Without checking for optimizing state the resizing operation takes far
too long and hence we are going to bring it back.
The reason for bringing optimizing check back is the root cause of previous flake was volume was entering desired size before it was done being modified (so
describeVolumereports higher size while volume is still being modified), so optimizing state was not root of the problem.On the other hand - not checking for optimizing state makes resizing very slow
This fixes https://bugzilla.redhat.com/show_bug.cgi?id=1810470